PK70394: CLASSNOTFOUNDEXCEPTION WHEN RUNNING J2EE APPLICATION CLIENT USING A RUN CONFIGURATION IN RATIONAL APPLICATION DEVELOPER

Rational Application Developer for WebSphere Software, Version 7.0.0.8
6.1.1.8: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 8

APAR status

• Closed as program error.

Error description

• The application client launcher in RAD does not work correctly
  with a non single-root application module.  A non single-root
  application module is one that has a separate source and output
  folder.
  
  Running this type of application client from the configuration
  launcher may work okay the first time, but on the second attempt
  it will cause ClassNotFoundException.
  

Local fix

• The simple (and preferred) work-around is to ensure that the
  source and output folder is the same.  A newly constructed
  application module will do this automatically.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  Toolkit v6.1.1 and Rational Application     *
  *                  Developer v7.0                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Subsequent launches of a J2EE           *
  *                      Application Client may cause            *
  *                      a ClassNotFoundException at runtime.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The J2EE WebSphere Application Client launcher toggles
  between running the client from the 'deployable1' and
  'deployable2' directories found in the .metadata when running
  a non single-root J2EE Application Client module.  In some
  scenarios the toggling fails and the application client always
  launches the content from the 'deployable1' directory even if
  the new content is published to the 'deployable2' directory.
  

Problem conclusion

• The J2EE WebSphere Application Client launcher will now
  correctly toggle between the 'deployable1' and 'deployable2'
  directories found in the .metadata when running a non
  single-root J2EE Application Client module.
  
  The fix for this APAR is currently targeted for inclusion in
  the WebSphere Application Server Toolkit fixpack 6.1.1.8  and
  Rational Application Developer fixpack 7.0.0.8.  Please refer
  to the following Recommended Updates page for WebSphere
  Application Server Toolkit delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27004980
  and the following Recommended Updates page for Rational
  Application Developer delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27007823
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R610 PSY

     UP